Type of change

• Bugfix

Description

#12067 describes a pretty nasty bug in our CRDs. The additional volumes in the Pod template use the native Fabric8 EmptyDirVolumeSource class in the API model. However, this class relies on the Fabric8 Quantity class and this class has a structure that our CRDs cannot handle. As a result:

• The CRDs have a wrong structure for configuring the size limit of the emptyDir volumes, which does not allow using the right Kubernetes format:

            emptyDir:
              sizeLimit: 10Mi
              medium: Memory

  and instead expects something like this:

            emptyDir:
              sizeLimit:
                amount: 10
                format: Gi
              medium: Memory

• However, even with the wrong format generated into the CRDs, Strimzi cannot decode the it and it cannot be used.

This PR creates our own model class to replace the Fabric8 EmptyDirVolumeSource. It does not use Quantity (similarly to our storage configuration) and makes sure the CRDs use the correct layout and Strimzi can handle it.

However, strictly speaking, this breaks the compatibility of the API. Given that it:

• Introduces the correct layout intended from the beginning
• This does not work in the existing CRDs / layout anyway
• This is the first complaint about it, so nobody seems ti be using it

I think it might be ok to do this. But there is some extent of risk worth considering during the review.

This should resolve #12067

Checklist

• Write tests
• Make sure all tests pass
• Update documentation
• Try your changes from Pod inside your Kubernetes and OpenShift cluster, not just locally
• Reference relevant issue(s) and close them after merging